Building management system with optimized processing of building system data

ABSTRACT

A building management system includes a plurality of meters configured to provide data samples of a plurality of points relating to a building and a space hierarchy database configured to store a sibling relationship for each of the points. Each sibling relationship identifies two or more of the points as sibling points. The building management system includes a batch metrics engine configured to receive a first data sample of a first point, access the sibling relationship for the first point to identify one or more sibling points of the first point, aggregate the first data sample with data samples of the sibling points to generate a batch, and calculate an aggregate metric using the first data sample and the other data samples in the batch. The building management system also includes a controller configured to adjust an operation of building equipment based on the aggregate metric.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/062,009 filed Oct. 2, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/051,992 filed Aug. 1, 2018, which claims thebenefit of and priority to Indian Provisional Patent Application No.201721040778 filed Nov. 15, 2017. The entire disclosure of each of theaforementioned patent applications is incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to a building management system(BMS) and more particularly to a BMS with enterprise management andreporting. A BMS is, in general, a system of devices configured tocontrol, monitor, and manage equipment in or around a building orbuilding area. A BMS can include, for example, an HVAC system, asecurity system, a lighting system, a fire alerting system, any othersystem that is capable of managing building functions or devices, or anycombination thereof.

A BMS includes a variety of meters distributed in multiple spaces andconnected to a central system for collection and analysis of data.Meters correspond to a point against which its metric is recordedperiodically. Each point is periodically recorded resulting in a samplethat includes the point, a timestamp, and the metric value at the timeof measurement. Spaces, subspaces, meters, and points may be arrangedhierarchically, so that all the meters and points below a space arerelevant to calculating metric values for that space. For purposes ofeffective analytics in a BMS, metrics may be desired at every level andfor different time aggregations (e.g., hourly, daily, monthly, yearly).For a large BMS with complex hierarchies, computation of these metricstraditionally becomes cumbersome and slow, resulting in poor performinguser interfaces, slow calculation of key performance indicators, anddifficulty in applying business rules to the metrics.

SUMMARY

One implementation of the present disclosure is a building managementsystem. The building management system includes a plurality of metersconfigured to provide data samples of a plurality of points relating toa building. The building includes a plurality of spaces. Each of thepoints is associated with at least one of the plurality of spaces. Thebuilding management system also includes a space hierarchy databaseconfigured to store a sibling relationship for each of the points. Eachsibling relationship identifies two or more of the points as siblingpoints. The building management system also includes a batch metricsengine configured to receive a first data sample of a first point,access the sibling relationship for the first point to identify one ormore sibling points of the first point, aggregate the first data samplewith one or more other data samples of the sibling points to generate abatch, and calculate an aggregate metric using the first data sample andthe one or more other data samples in the batch. The building managementsystem also includes a controller configured to adjust an operation ofbuilding equipment based on the aggregate metric. The building equipmentis operable to affect the plurality of points.

In some embodiments, the first point is provided by a first meter of theplurality of meters and the one or more sibling points are provided byone or more sibling meters of the plurality of meters. The first meteris associated with a first space and the one or more sibling meters areassociated with one or more sibling spaces. The first space and the oneor more sibling spaces are located within a common parent space.

In some embodiments, the batch metrics engine is configured to generatethe batch and calculate the aggregate metric in response to receivingthe first data sample. In some embodiments, the building managementsystem also includes a timeseries storage database configured to storethe data samples of the plurality of points. Each of the data samplesinclude a time stamp and a value of at least one of the one or morepoints.

In some embodiments, the bath metrics engine is configured to aggregatethe first data sample and the one or more data samples of the siblingpoints to generate the batch by determining a relevant time period forcalculating the aggregate metric, selecting one or more of the datasamples of the sibling points that have timestamps within the relevanttime period in the timeseries storage database, and retrieving theselected data samples from the timeseries storage database.

In some embodiments, the building management system also includes acurrent metrics database configured to store the aggregate metric. Insome embodiments, the building analytics and presentation circuit isconfigured to access the aggregate metric in the current metricsdatabase and generate a graphical user interface that presents theaggregate metric to a user.

In some embodiments, the building management system also includes abuilding analytics and presentation circuit configured to access theaggregate metric and a plurality of additional metrics in the currentmetric database and calculate an advanced metric based on the aggregatemetric and the plurality of additional metrics.

Another implementation of the present disclosure is a method formanaging a building. The method includes providing, by a plurality ofmeters, data samples of a plurality of points relating to the building.The building includes a plurality of spaces. Each of the points isassociated with at least one of the plurality of spaces. The method alsoincludes storing, by a space hierarchy database, a sibling relationshipfor each of the points. Each sibling relationship identifies two or moreof the points as sibling points. The method also includes receiving, ata batch metrics engine, a first data sample of a first point, accessing,by the batch metrics engine, the space hierarchy database to identifyone or more sibling points of the first point based on the siblingrelationship for the first point, aggregating, by the batch metricsengine, the first data sample with one or more other data samples of thesibling points to generate a batch, calculating, by the batch metricsengine, an aggregate metric using the first data sample and the one ormore data samples in the batch, and adjusting an operation of buildingequipment based on the aggregate metric to affect the plurality ofpoints.

In some embodiments, the first point is provided by a first meter of theplurality of meters and the one or more sibling points are provided byone or more sibling meters of the plurality of meters. The first meteris associated with a first space and the one or more sibling meters areassociated with one or more sibling spaces. The first space and the oneor more sibling spaces are located within a common parent space.

In some embodiments, receiving the first data sample triggers the batchmetrics engine to generate the batch and calculate the aggregate metricusing the data samples in the batch. In some embodiments, the methodincludes storing the data samples provided by the plurality of points ina timeseries storage database. Each of the data samples includes a timestamp and a value of at least one of the plurality of points.

In some embodiments, aggregating, by the batch metrics engine, the firstdata sample and the one or more data samples of the sibling points togenerate the batch includes determining a relevant time period forcalculating the aggregate metric, selecting one or more of the datasamples of the sibling points that have timestamps within the relevanttime period in the timeseries storage database, and retrieving theselected data samples from the timeseries storage database.

In some embodiments, the method also includes storing the aggregatemetric in a current metrics database. In some embodiments, the methodalso includes accessing the aggregate metric in the current metricsdatabase and generating a graphical user interface that presents theaggregate metric to a user.

In some embodiments, the method also includes accessing the aggregatemetric and a plurality of additional metrics in the current metricdatabase and calculating an advanced metric based on the aggregatemetric and the plurality of additional metrics.

Another implementation of the present disclosure is a method formanaging a building. The method includes collecting, by a plurality ofmeters, data samples corresponding to a plurality of points associatedwith a plurality of spaces of the building. The spaces are arranged in aspace hierarchy. The method also includes determining sets of siblingpoints based on the space hierarchy. Each set of sibling pointscorresponds to a metric for a space in the space hierarchy. The methodalso includes aggregating, for each set of sibling points, data samplescorresponding to the sibling points, calculating the metrics based onthe aggregated data samples to generate calculated values for themetrics, and controlling building equipment based on the calculatedmetrics to operate to affect a variable state or condition of thebuilding.

In some embodiments, the method also includes storing the calculatedvalues for the metrics in a database, receiving a request from a user toview one or more of the metrics, in response to the request, retrievingthe calculated values for the one or more metrics from the database, andproviding the calculated values for the one or more metrics on agraphical user interface.

In some embodiments, the method includes associating each data samplewith a time stamp and a point, and storing the data sample, the timestamp, and the point in a timeseries storage database. In someembodiments, aggregating, for each set of sibling points, data samplescorresponding to the sibling points includes determining a relevant timeperiod for calculating a first metric, and identifying the data samplesfrom the relevant time period based on the time stamps.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto some embodiments.

FIG. 2 is a block diagram of a waterside system which can be used toserve the building of FIG. 1 , according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used toserve the building of FIG. 1 , according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) whichcan be used to monitor and control the building of FIG. 1 , according tosome embodiments.

FIG. 5 is a block diagram of another BMS which can be used to monitorand control the building of FIG. 1 , according to some embodiments.

FIG. 6 is a block diagram of a space hierarchy, according to anexemplary embodiment.

FIG. 7 is a block diagram of a metric generation system, which can beimplemented as a component of the BMSs of FIGS. 4-5 , according to anexemplary embodiment.

FIG. 8 is flowchart of a method of batch processing building metrics,which can be performed by the BMSs of FIGS. 4-5 , according to anexemplary embodiment.

DETAILED DESCRIPTION Building HVAC Systems and Building ManagementSystems

Referring now to FIGS. 1-5 , several building management systems (BMS)and HVAC systems in which the systems and methods of the presentdisclosure can be implemented are shown, according to some embodiments.In brief overview, FIG. 1 shows a building 10 equipped with a HVACsystem 100. FIG. 2 is a block diagram of a waterside system 200 whichcan be used to serve building 10. FIG. 3 is a block diagram of anairside system 300 which can be used to serve building 10. FIG. 4 is ablock diagram of a BMS which can be used to monitor and control building10. FIG. 5 is a block diagram of another BMS which can be used tomonitor and control building 10.

Building and HVAC System

Referring particularly to FIG. 1 , a perspective view of a building 10is shown. Building 10 is served by a BMS. A BMS is, in general, a systemof devices configured to control, monitor, and manage equipment in oraround a building or building area. A BMS can include, for example, aHVAC system, a security system, a lighting system, a fire alertingsystem, any other system that is capable of managing building functionsor devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3 .

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1 ) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2 , a block diagram of a waterside system 200 isshown, according to some embodiments. In various embodiments, watersidesystem 200 may supplement or replace waterside system 120 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 can belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2 , waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve thermal energy loads (e.g.,hot water, cold water, heating, cooling, etc.) of a building or campus.For example, heater subplant 202 can be configured to heat water in ahot water loop 214 that circulates the hot water between heater subplant202 and building 10. Chiller subplant 206 can be configured to chillwater in a cold water loop 216 that circulates the cold water betweenchiller subplant 206 building 10. Heat recovery chiller subplant 204 canbe configured to transfer heat from cold water loop 216 to hot waterloop 214 to provide additional heating for the hot water and additionalcooling for the cold water. Condenser water loop 218 may absorb heatfrom the cold water in chiller subplant 206 and reject the absorbed heatin cooling tower subplant 208 or transfer the absorbed heat to hot waterloop 214. Hot TES subplant 210 and cold TES subplant 212 may store hotand cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve thermal energy loads. In otherembodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Airside System

Referring now to FIG. 3 , a block diagram of an airside system 300 isshown, according to some embodiments. In various embodiments, airsidesystem 300 may supplement or replace airside system 130 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3 , airside system 300 is shown to include an economizer-typeair handling unit (AHU) 302. Economizer-type AHUs vary the amount ofoutside air and return air used by the air handling unit for heating orcooling. For example, AHU 302 may receive return air 304 from buildingzone 306 via return air duct 308 and may deliver supply air 310 tobuilding zone 306 via supply air duct 312. In some embodiments, AHU 302is a rooftop unit located on the roof of building 10 (e.g., AHU 106 asshown in FIG. 1 ) or otherwise positioned to receive both return air 304and outside air 314. AHU 302 can be configured to operate exhaust airdamper 316, mixing damper 318, and outside air damper 320 to control anamount of outside air 314 and return air 304 that combine to form supplyair 310. Any return air 304 that does not pass through mixing damper 318can be exhausted from AHU 302 through exhaust damper 316 as exhaust air322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3 , AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU 330 maycontrol the temperature of supply air 310 and/or building zone 306 byactivating or deactivating coils 334-336, adjusting a speed of fan 338,or a combination of both.

Still referring to FIG. 3 , airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3 ) or integrated. Inan integrated implementation, AHU controller 330 can be a softwarecircuit configured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Building Management Systems

Referring now to FIG. 4 , a block diagram of a building managementsystem (BMS) 400 is shown, according to some embodiments. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3 .

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3. For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices and servers, or other security-related devices.

Still referring to FIG. 4 , BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4 , BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and circuits described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to someembodiments, memory 408 is communicably connected to processor 406 viaprocessing circuit 404 and includes computer code for executing (e.g.,by processing circuit 404 and/or processor 406) one or more processesdescribed herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4 , memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translates communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to some embodiments, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a controlcircuit configured to actively initiate control actions (e.g.,automatically changing setpoints) which minimize energy costs based onone or more inputs representative of or based on demand (e.g., price, acurtailment signal, a demand level, etc.). In some embodiments, demandresponse layer 414 uses equipment models to determine an optimal set ofcontrol actions. The equipment models can include, for example,thermodynamic models describing the inputs, outputs, and/or functionsperformed by various sets of building equipment. Equipment models mayrepresent collections of building equipment (e.g., subplants, chillerarrays, etc.) or individual devices (e.g., individual chillers, heaters,pumps, etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML, files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In some embodiments, integrated control layer418 includes control logic that uses inputs and outputs from a pluralityof building subsystems to provide greater comfort and energy savingsrelative to the comfort and energy savings that separate subsystemscould provide alone. For example, integrated control layer 418 can beconfigured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 may compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 may receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 may automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to some embodiments, FDD layer 416 (ora policy executed by an integrated control engine or business rulesengine) may shut-down systems or direct control activities around faultydevices or systems to reduce energy waste, extend equipment life, orassure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Referring now to FIG. 5 , a block diagram of another building managementsystem (BMS) 500 is shown, according to some embodiments. BMS 500 can beused to monitor and control the devices of HVAC system 100, watersidesystem 200, airside system 300, building subsystems 428, as well asother types of BMS devices (e.g., lighting equipment, securityequipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automaticequipment discovery and equipment model distribution. Equipmentdiscovery can occur on multiple levels of BMS 500 across multipledifferent communications busses (e.g., a system bus 554, zone buses556-560 and 564, sensor/actuator bus 566, etc.) and across multipledifferent communications protocols. In some embodiments, equipmentdiscovery is accomplished using active node tables, which provide statusinformation for devices connected to each communications bus. Forexample, each communications bus can be monitored for new devices bymonitoring the corresponding active node table for new nodes. When a newdevice is detected, BMS 500 can begin interacting with the new device(e.g., sending control signals, using data from the device) without userinteraction.

Some devices in BMS 500 present themselves to the network usingequipment models. An equipment model defines equipment objectattributes, view definitions, schedules, trends, and the associatedBACnet value objects (e.g., analog value, binary value, multistatevalue, etc.) that are used for integration with other systems. Somedevices in BMS 500 store their own equipment models. Other devices inBMS 500 have equipment models stored externally (e.g., within otherdevices). For example, a zone coordinator 508 can store the equipmentmodel for a bypass damper 528. In some embodiments, zone coordinator 508automatically creates the equipment model for bypass damper 528 or otherdevices on zone bus 558. Other zone coordinators can also createequipment models for devices connected to their zone busses. Theequipment model for a device can be created automatically based on thetypes of data points exposed by the device on the zone bus, device type,and/or other device attributes. Several examples of automatic equipmentdiscovery and equipment model distribution are discussed in greaterdetail below.

Still referring to FIG. 5 , BMS 500 is shown to include a system manager502; several zone coordinators 506, 508, 510 and 518; and several zonecontrollers 524, 530, 532, 536, 548, and 550. System manager 502 canmonitor data points in BMS 500 and report monitored variables to variousmonitoring and/or control applications. System manager 502 cancommunicate with client devices 504 (e.g., user devices, desktopcomputers, laptop computers, mobile devices, etc.) via a datacommunications link 574 (e.g., BACnet IP, Ethernet, wired or wirelesscommunications, etc.). System manager 502 can provide a user interfaceto client devices 504 via data communications link 574. The userinterface may allow users to monitor and/or control BMS 500 via clientdevices 504.

In some embodiments, system manager 502 is connected with zonecoordinators 506-510 and 518 via a system bus 554. System manager 502can be configured to communicate with zone coordinators 506-510 and 518via system bus 554 using a master-slave token passing (MSTP) protocol orany other communications protocol. System bus 554 can also connectsystem manager 502 with other devices such as a constant volume (CV)rooftop unit (RTU) 512, an input/output circuit (IOM) 514, a thermostatcontroller 516 (e.g., a TEC5000 series thermostat controller), and anetwork automation engine (NAE) or third-party controller 520. RTU 512can be configured to communicate directly with system manager 502 andcan be connected directly to system bus 554. Other RTUs can communicatewith system manager 502 via an intermediate device. For example, a wiredinput 562 can connect a third-party RTU 542 to thermostat controller516, which connects to system bus 554.

System manager 502 can provide a user interface for any devicecontaining an equipment model. Devices such as zone coordinators 506-510and 518 and thermostat controller 516 can provide their equipment modelsto system manager 502 via system bus 554. In some embodiments, systemmanager 502 automatically creates equipment models for connected devicesthat do not contain an equipment model (e.g., IOM 514, third partycontroller 520, etc.). For example, system manager 502 can create anequipment model for any device that responds to a device tree request.The equipment models created by system manager 502 can be stored withinsystem manager 502. System manager 502 can then provide a user interfacefor devices that do not contain their own equipment models using theequipment models created by system manager 502. In some embodiments,system manager 502 stores a view definition for each type of equipmentconnected via system bus 554 and uses the stored view definition togenerate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or moreof zone controllers 524, 530-532, 536, and 548-550 via zone buses 556,558, 560, and 564. Zone coordinators 506-510 and 518 can communicatewith zone controllers 524, 530-532, 536, and 548-550 via zone busses556-560 and 564 using a MSTP protocol or any other communicationsprotocol. Zone busses 556-560 and 564 can also connect zone coordinators506-510 and 518 with other types of devices such as variable air volume(VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552,bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor andcommand various zoning systems. In some embodiments, each zonecoordinator 506-510 and 518 monitors and commands a separate zoningsystem and is connected to the zoning system via a separate zone bus.For example, zone coordinator 506 can be connected to VAV RTU 522 andzone controller 524 via zone bus 556. Zone coordinator 508 can beconnected to COBP RTU 526, bypass damper 528, COBP zone controller 530,and VAV zone controller 532 via zone bus 558. Zone coordinator 510 canbe connected to PEAK controller 534 and VAV zone controller 536 via zonebus 560. Zone coordinator 518 can be connected to PEAK controller 544,bypass damper 546, COBP zone controller 548, and VAV zone controller 550via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured tohandle multiple different types of zoning systems (e.g., a VAV zoningsystem, a COBP zoning system, etc.). Each zoning system can include aRTU, one or more zone controllers, and/or a bypass damper. For example,zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs)connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 isconnected directly to VAV RTU 522 via zone bus 556, whereas zonecoordinator 510 is connected to a third-party VAV RTU 540 via a wiredinput 568 provided to PEAK controller 534. Zone coordinators 508 and 518are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and552, respectively. Zone coordinator 508 is connected directly to COBPRTU 526 via zone bus 558, whereas zone coordinator 518 is connected to athird-party COBP RTU 552 via a wired input 570 provided to PEAKcontroller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate withindividual BMS devices (e.g., sensors, actuators, etc.) viasensor/actuator (SA) busses. For example, VAV zone controller 536 isshown connected to networked sensors 538 via SA bus 566. Zone controller536 can communicate with networked sensors 538 using a MSTP protocol orany other communications protocol. Although only one SA bus 566 is shownin FIG. 5 , it should be understood that each zone controller 524,530-532, 536, and 548-550 can be connected to a different SA bus. EachSA bus can connect a zone controller with various sensors (e.g.,temperature sensors, humidity sensors, pressure sensors, light sensors,occupancy sensors, etc.), actuators (e.g., damper actuators, valveactuators, etc.) and/or other types of controllable equipment (e.g.,chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured tomonitor and control a different building zone. Zone controllers 524,530-532, 536, and 548-550 can use the inputs and outputs provided viatheir SA busses to monitor and control various building zones. Forexample, a zone controller 536 can use a temperature input received fromnetworked sensors 538 via SA bus 566 (e.g., a measured temperature of abuilding zone) as feedback in a temperature control algorithm. Zonecontrollers 524, 530-532, 536, and 548-550 can use various types ofcontrol algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control a variable state or condition (e.g., temperature, humidity,airflow, lighting, etc.) in or around building 10.

Metrics Generation System with Optimized Processing of Meter Data

Referring generally to FIGS. 6-8 , a system and method for optimizedprocessing of building automation system data are shown, according toexemplary embodiments. A BMS, for example as described above withreference to FIGS. 4-5 , includes a range of sensor and controllersconnected to a central system for collection and analysis of data. Forthe purpose of measurement, meters can be installed in multiple spacesof the building or buildings. Meters may contain one or more sensorsthat measure a metric like electric demand, consumption, power factor,and occupancy, among other possible metrics. Each sensor may correspondto a point against which its metric is recorded periodically. Each pointmay be periodically recorded resulting in a sample that includes thepoint, a timestamp, and the metric value at the time of measurement.Spaces, meters, and points may be arranged hierarchically. The spaces,meters, and points that contribute to a space may be termed the childrenof the space, and the space may be termed the parent of the spaces,meters, and points that contribute to it. All points that measure thesame metric and are children of the same space may be labelled assiblings.

Referring now to FIG. 6 , a block diagram of a BMS space hierarchy isshown, according to an exemplary embodiment. A portfolio 600 managed bya BMS (e.g., BMS 500, BMS 400) includes equipment (e.g., HVAC system100) located in multiple buildings 602, shown as Building A and BuildingB. Building A and Building B are both made up of multiple floors 604,arranged one level below to indicate that the floors 604 are subspacesof the buildings 602. For example, Floor A1, Floor A2, . . . , and FloorAn are children of Building A. Within each floor are one or more wings606, arranged to indicate that each wing is a subspace of a specificfloor 604 as well as a subspace of a building 602. For example, WingA11, Wing A12, and Wing A13 are shown as children of Floor A1 andBuilding A. Building B is arranged similarly. It should be understoodthat the hierarchy of FIG. 6 is included for illustrative purposes andthat the systems and methods disclosed herein are suitable forapplication with various collections of campuses, enterprises,buildings, spaces, subspaces, sub-subspaces and so forth.

Meters 608 may be positioned at various levels in the hierarchy,including at the level of the Floors in the hierarchy and at the levelof the Wings in the hierarchy. The meters 608 may include sensors thatmeasure one or more physical parameters relating to the correspondingfloor or wing to generate data samples of points corresponding to thephysical parameters. Meters 608 may also generate data samples directlyat the building 602 or portfolio 600 level, or various other levels in ahierarchy of any embodiment. Meters 608 may be physically located at anassociated space as well as virtually associated with the space in aspace hierarchy database, for example as described in detail below.

FIG. 6 illustrates that at least two scenarios are possible whendetermining a value of a metric for a space in the BMS space hierarchy(i.e., for a portfolio 600, a building 602, a floor 604, a wing 606,etc.). First, if a relevant meter 608 is directly associated with aspace on the level of that space (e.g., shown on that space in FIG. 6 ),then the value of a metric for the space may be equal to a sample fromthat meter. For example, a metric for Floor Al of Building A is directlymeasured by the meter 608 shown as associated with Floor Al. Second, ifno relevant meter 608 is connected to the space at the level of thespace, then the value of a metric may be derived by aggregating valuesmeasured by meters 608 of children of that space. For example, a metricfor Building 2 may be calculated based on measurements the meters 608 atFloor B1, Floor B2, Wing Bn1, and Wing Bn3.

For purposes of effective analytics in a BMS, metrics may be required atevery level and for different time aggregations (e.g., hourly, daily,monthly, yearly). For a large BMS with complex hierarchies, computationof these metrics traditionally becomes cumbersome and slow, resulting inpoor performing user interfaces, slow calculation of key performanceindicators, and difficulty in applying business rules to the metrics. Asdiscussed in detail with respect to FIGS. 7-8 , metrics for each spaceand each level of time aggregation may be pre-calculated and storedusing a batch processing approach to address these challenges.

Referring now to FIG. 7 , a block diagram of a metrics generation system700 is shown, according to an exemplary embodiment. In some embodiments,the metrics generation system 700 is a component of a BMS, such as BMS400 or BMS 500 described with reference to FIGS. 4-5 . The metricsgeneration system 700 includes a space hierarchy database 702, atimeseries storage database 704, a current metrics database 706, and abatch metrics engine 708. The metrics generation system 700 iscommunicably coupled to multiple meters 608, a building analytics andpresentation circuit 710 and an equipment controller 712.

Meters 608 are shown within a building sub-space 750 and a building 751.In other embodiments, more meters and/or more buildings and/or buildingsub-spaces may be included. The meters 608 take readings (i.e., measurephysical parameters) to generate data samples corresponding to points,label the samples with timestamps, and transmit those samples to themetrics generation system 700 periodically or non-periodically. Raw datasamples and the corresponding point and timestamp data are stored in atimeseries storage database 706.

The space hierarchy database 702 is configured to store a spacehierarchy for the spaces managed by a BMS. As described above inreference to FIG. 6 , buildings, spaces, subspaces, meters, and pointsare arranged hierarchically based on parent and child relationships.These relationships may be stored in the space hierarchy database 702.That is, the space hierarchy database 702 may store a list of parentsand children for each entity in the space hierarchy.

The space hierarchy database 702 also stores sibling relationshipsbetween sibling points. Sibling points are points that provide the samemetric and that share a common parent space. Sibling points may beinitially defined by a user or may be automatically recognized by themetrics generation system. Various data models and/or data objects maybe used in various embodiments to indicate sibling relationships. Forexample, the space hierarchy database 702 may store a list of siblingpoints for each point in the hierarchy, a list of sibling spaces of eachspace in the hierarchy, etc.

The timeseries storage database 704 receives and stores timeseries datasamples for points from the meters 608. The timeseries storage database704 may be communicable with the batch metrics engine 708 to allow thebatch metrics engine 708 to access (i.e., use, copy, etc.) thetimeseries data in the timeseries storage database 704.

The batch metrics engine 708 is configured to calculate metrics for alllevels of the space hierarchy and store them in the current metricsdatabase 706 where the metrics can be accessed on demand by the buildinganalytics and presentation circuit 710. The batch metrics engine 708calculates metrics using a batch processing method, for example asdescribed below in reference to FIG. 8 . The batch metrics engine 708may be triggered to calculate one or more updated metrics when themetrics generation system 700 receives a new data sample from a meter608. In other embodiments, updates to metrics may be prescheduled orrepeated after a set time interval. The batch metrics engine 708accesses the space hierarchy database 706 to determine if calculatingthe metric requires aggregating data from multiple meters 608. Thedetermination may include checking whether the space is a parent ofmultiple meters that provide samples of that metric, or by checking if apoint has at least one sibling. If aggregation is required (i.e., if thespace is a parent of multiple meters or if the point has one or moresibling points), the batch metrics engine accesses the siblingrelationships in the space hierarchy database to identify all siblingsof the point. By using stored sibling relationships, the batch metricsengine 708 avoids re-analyzing the parent-child hierarchy to locatesibling points for every calculation. The batch metrics engine 708 alsoidentifies a time period over which to run the calculation, which may bebased on the timespan of the corresponding metric (e.g., one hour, oneweek, one month, three months, one year). The batch metrics engine 708then pulls data samples for each of the siblings for this time periodfrom the timeseries storage database 704. For example, if the identifiedtime period is one hour, the batch metrics engine 708 will access datasamples from all sibling points with a timestamp from the last hour. Thebatch metrics engine 708 calculates an updated metric based on the datasamples, and stores the result in the current metrics database 706.

Up-to-date metrics are thereby stored in the current metrics database706. A building analytics and presentation circuit 710 may access thecurrent metrics database 706 at any time to run higher-level analyticson the up-to-date metrics without recalculating metrics from raw datasamples. The building analytics and presentation circuit 710 may alsoaccess the up-to-date metrics for inclusion in a graphical userinterface generated by the building analytics and presentation circuit710 for presentation to a user without the need to calculate metricsfrom raw data on demand. A user may therefore have a quicker, smootherexperience viewing metrics for the building, building sub-space, etc. ina graphical user interface.

The equipment controller 712 may also access the current metricsdatabase 706 to receive one or more metrics from the current metricsdatabase 706. The equipment controller 712 may generate control signalsfor building equipment based on the one or more metrics. For example,the equipment controller 712 may turn building equipment on or off,increase or decrease an operating power of the building equipment,adjust a setpoint (e.g., a temperature setpoint) for the buildingequipment, etc. The building equipment may be operable to affect thepoints and/or metrics, such that the equipment controller 712 maycontrol the building equipment to cause a change in the value of one ormore points and/or one or more metrics over time.

Referring now to FIG. 8 , a flowchart showing a process 800 for batchprocessing of building metrics is shown. When new data samples arereceived for a point, the values for the metrics for all of the point'sparents may be updated. Batch data processing as shown in the FIG. 8 isused to group together data received for different children of a spacefor the purpose of reducing the number of updates to the parent space'smetrics. This batch data processing 800 of FIG. 8 is therefore moreefficient, requires less computing resources, and provides up-to-datemetrics accessible to a user or other system.

To start, at step 802, new data samples for a point are taken (i.e.,collected by a meter 608 and received by the metric generation system700). Receiving a new data sample initiates process 800, i.e., triggersthe metrics generation system to calculate one or more updated metrics.At step 804, the batch metrics engine 708 determines whether dataaggregation is required, i.e., whether data from more than one meter isrequired to calculate a metric based on the new data sample. If dataaggregation is not required—for example, when the metric is directlymeasured by a single meter—then the relevant sample is enough todetermine a value of the metric and the process ends.

If space aggregation is required (i.e., multiple points are all relevantto a desired metric), then the batch processing method is initiatedfollowing step 804. At step 806, sibling points of the point of the newdata sample are identified based on space hierarchy information storedin the space hierarchy database 702. Siblings include all other pointsfor the same metric that are children of the same space, i.e., childrenof the space for which a metric is to be calculated. In someembodiments, the space hierarchy database 702 stores a list of siblingpoints for each point, such that at step 804 the batch metrics engine708 looks up the point in the space hierarchy database 702 to determinethe other points that are used to calculate a metric. This providessubstantial efficiencies over other approaches which may requirereanalysis of the hierarchy to re-identify such points each time ametric is to be calculated.

At step 808, a period of calculation is identified, corresponding to atime period over which samples from all siblings will be collected. Theperiod of calculation may be dependent on the type of metric to becalculated. At step 810, the data for all siblings (as identified atstep 806) over the period of calculation (as identified at step 808) isfetched from the timeseries storage database 704. This data is collectedin a batch of data along with the new data sample received at step 802.At step 812, a mapping of the points (i.e., the collection of siblingpoints) to a parent space is retrieved from the space hierarchy database702. That is, the batch metrics engine 708 identifies the parent spacecorresponding to a metric calculated based on the aggregation of datacorresponding to the sibling points identified at step 810.

At step 814, an aggregate metric for the parent space identified at step812 is calculated based on the batch of data. The aggregate metric maybe a sum of the metrics for child spaces of the parent space or may becalculated using any other algorithm.

At step 816, the aggregate metric for the parent space is stored in thecurrent metrics database 706. The current metrics database 706 may thenbe accessed by the building analytics and presentation circuit 710 foruse in meta-analysis and/or for integration into a graphical userinterface accessible by a user.

Using this method, the value of all metrics at all levels within aportfolio may be automatically updated to be available for use. The timerequired to fetch the metrics (e.g., in response to a user request, forthe purpose of running business rules) is reduced by thepre-calculation, and the batching method may substantially reduce thecalculation load on the BMS processors.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure can be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps canbe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

1-20. (canceled)
 21. A building management system comprising: aplurality of meters configured to provide data samples of a plurality ofpoints relating to a building, the building comprising a plurality ofspaces, the plurality of points associated with at least one of theplurality of spaces; a space hierarchy database configured to storesibling relationships for the plurality of points, the siblingrelationships identifying two or more of the plurality of points assibling points; and a batch metrics engine configured to: receive afirst data sample of a first point; access a sibling relationship of thesibling relationships for the first point to identify one or moresibling points of the first point; aggregate the first data sample withone or more other data samples of the one or more sibling points togenerate a batch; and calculate an aggregate metric using the first datasample and the one or more other data samples in the batch.
 22. Thebuilding management system of claim 21, wherein: the first point isprovided by a first meter of the plurality of meters and the one or moresibling points are provided by one or more sibling meters of theplurality of meters; the first meter is associated with a first spaceand the one or more sibling meters are associated with one or moresibling spaces; and the first space and the one or more sibling spacesare located within a common parent space.
 23. The building managementsystem of claim 21, wherein the batch metrics engine is configured togenerate the batch and calculate the aggregate metric in response toreceiving the first data sample.
 24. The building management system ofclaim 21, further comprising: a controller configured to adjust anoperation of building equipment based on the aggregate metric, thebuilding equipment operable to affect the plurality of points; and atimeseries storage database configured to store the data samples of theplurality of points, each of the data samples comprising a time stampand a value of at least one of the one or more points.
 25. The buildingmanagement system of claim 24, wherein the batch metrics engine isconfigured to aggregate the first data sample and the one or more otherdata samples of the sibling points to generate the batch by: determininga time period for calculating the aggregate metric; selecting one ormore of the one or more other data samples of the sibling points thathave timestamps within the time period in the timeseries storagedatabase; and retrieving selected data samples from the timeseriesstorage database.
 26. The building management system of claim 21,further comprising a current metrics database configured to store theaggregate metric.
 27. The building management system of claim 26,further comprising a building analytics and presentation circuitconfigured to: access the aggregate metric in the current metricsdatabase; and generate a graphical user interface that presents theaggregate metric to a user.
 28. The building management system of claim26, further comprising a building analytics and presentation circuitconfigured to: access the aggregate metric and a plurality of additionalmetrics in the current metrics database; and calculate an advancedmetric based on the aggregate metric and the plurality of additionalmetrics.
 29. A method for managing a building, comprising: providing, bya plurality of meters, data samples of a plurality of points relating tothe building, the building comprising a plurality of spaces, theplurality of points associated with at least one of the plurality ofspaces; storing, by a space hierarchy database, sibling relationshipsfor the plurality of points, the sibling relationships identifying twoor more of the plurality of points as sibling points; receiving, at abatch metrics engine, a first data sample of a first point; accessing,by the batch metrics engine, the space hierarchy database to identifyone or more sibling points of the first point based on a siblingrelationship of the sibling relationships for the first point;aggregating, by the batch metrics engine, the first data sample with oneor more other data samples of the one or more sibling points to generatea batch; and calculating, by the batch metrics engine, an aggregatemetric using the first data sample and the one or more other datasamples in the batch.
 30. The method of claim 29, wherein: the firstpoint is provided by a first meter of the plurality of meters and theone or more sibling points are provided by one or more sibling meters ofthe plurality of meters; the first meter is associated with a firstspace and the one or more sibling meters are associated with one or moresibling spaces; and the first space and the one or more sibling spacesare located within a common parent space.
 31. The method of claim 29,wherein receiving the first data sample triggers the batch metricsengine to generate the batch and calculate the aggregate metric usingthe data samples in the batch.
 32. The method of claim 29, comprising:storing the data samples provided by the plurality of points in atimeseries storage database, each of the data samples comprising a timestamp and a value of at least one of the plurality of points; andadjusting an operation of building equipment based on the aggregatemetric to affect the plurality of points.
 33. The method of claim 32,wherein aggregating, by the batch metrics engine, the first data sampleand the one or more other data samples of the sibling points to generatethe batch comprises: determining a time period for calculating theaggregate metric; selecting one or more of the data samples of thesibling points that have timestamps within the time period in thetimeseries storage database; and retrieving selected data samples fromthe timeseries storage database.
 34. The method of claim 29, furthercomprising storing the aggregate metric in a current metrics database.35. The method of claim 34, further comprising: accessing the aggregatemetric in the current metrics database; and generating a graphical userinterface that presents the aggregate metric to a user.
 36. The methodof claim 34, further comprising: accessing the aggregate metric and aplurality of additional metrics in the current metrics database; andcalculating an advanced metric based on the aggregate metric and theplurality of additional metrics.
 37. A method for managing a building,comprising: collecting, by a plurality of meters, data samplescorresponding to a plurality of points associated with a plurality ofspaces of the building, indications of the plurality of spaces of thebuilding arranged in a space hierarchy; determining sets of siblingpoints based on the space hierarchy, one set of sibling points of thesets of sibling points corresponding to a metric for a space in thespace hierarchy; aggregating, for the sets of sibling points, datasamples corresponding to the sets of sibling points; calculating metricsbased on the data samples to generate calculated values for the metrics.38. The method of claim 37, further comprising: storing the calculatedvalues for the metrics in a database; receiving a request from a user toview one or more of the metrics; in response to the request, retrievingthe calculated values for the one or more metrics from the database; andproviding the calculated values for the one or more metrics on agraphical user interface.
 39. The method of claim 37, furthercomprising: associating each data sample with a time stamp and a point;and storing the data sample, the time stamp, and the point in atimeseries storage database.
 40. The method of claim 39, whereinaggregating, for the sets of sibling points, data samples correspondingto the sets of sibling points comprises: determining a time period forcalculating a first metric; and identifying the data samples from thetime period based on time stamps.